Migrated from history panel legacy branch

After eba8385, plot_results creates a "Results" group in the signal
panel, breaking panel-wide index lookups. Use group-local lookups so
the test is robust against extra groups.

(cherry picked from commit 5e08f9c)
(cherry picked from commit b2c4965)

…cenarios

…get and HTML rendering

…el and related components

…story

…ages and replay actions

…ality

(cherry picked from commit 6807861)

…s and add new history panel entries

Split the history feature into dedicated modules, refresh the GUI wiring and widgets, and update the related tests and translations.

# Conflicts:
#	datalab/locale/fr/LC_MESSAGES/datalab.po
#	doc/locale/fr/LC_MESSAGES/release_notes/release_1.03.po
#	doc/release_notes/release_1.03.md

Follow-up to a review noting that ruff/pylint had not been run on the
History panel refactor after it was split into submodules. Cross-module
access to underscore-prefixed members triggered W0212, plus a batch of
other lint warnings that were addressed without disabling any checks.

Creation actions (new signal/image) were recorded in the history but, unlike process actions, could not be edited, recomputed or reverted. Editing a creation left downstream steps inconsistent. This makes creations first-class history actions: their parameters can be re-edited, the result is recomputed in place (keeping the UUID and downstream references), and the chain cascades correctly.

* [NEW] : Allow editing creation (new_object) parameters via dialog and recompute in place, preserving the output UUID so downstream actions stay linked

* [NEW] : Resolve target panel for UI creation actions so they replay and cascade like compute actions

* [CHG] : add_ui_entry now returns the created HistoryAction, enabling creation output_uuids to be registered for downstream resolution

* [CHG] : Restore/undo without saving now covers creation actions for both single action and full session

* [FIX] : Snapshot creation parameters on edit for proper export/import and revert

…ompute

Edit-mode replay opened parameter dialogs per selected action, each editing its own downstream chain. Overlapping chains caused repeated prompts and inconsistent state. Recompute also stopped at the edited action instead of cascading to the full downstream.

* [FIX] : Process selected actions once via edit_mode_replay_actions, with deduplication, session-order sorting and a re-entrance guard, instead of calling edit_mode_replay per action

* [FIX] : Replay only the selected actions; on param change, recompute in place then cascade fully downstream from the most upstream edited action

* [CHG] : Cancel restores parameter snapshots for already-edited actions

…pipelines